\section{Design Guidelines}
\subsection{Design Goals}\label{Design Goals}
\fancyfoot[C]{Design Goals}
Traditional CMSs are powerful technology solutions, but they often fall short and end up satisfying two distinct design extremes:
\begin{description}
\item[User-Friendly, Feature-limited]These CMSes rely extensively on user-friendly interfaces, but are limited to their basic functionality without significant modification. Canonical examples include WordPress and nopCommerce.
\item[Feature-Unlimited, User-Unfriendly]These CMSes are very feature-rich, with extensive libraries and utilities that can be utilized by the user. However, the majority of essential features apply only to the specific CMS environment, and are nontrivial to learn how to apply at best. Canonical examples include SiteCore and Drupal.
\end{description}
Siberia CMS attempts to shatter the myth that a CMS has to be an either-or proposition: This software is designed to be extensible and easy to use.
\begin{description}
\item[Web-based Administration]A staple of any CMS software, being able to administer via a Web interface provides twofold benefits: Graphically-oriented users as well as users geographically seperated from the server can use convenient administrative features, or supply intellectual assets remotely.
\item[Plugin Architecture]The ability to add and remove functionality at ease is common across many CMSes, but sites are defined not just by style, but by the variety of functionality that various well-supported plugins supply.
\item[Open API]When a need arises, developers harness existing features of the CMS to implement further functionality, in the form of new plugins.
\end{description}
%todo: browser
\subsection{Technologies Used}\label{TechnologiesUsed}We are designing this software to utilize the .NET Framework, and be used in conjunction with a web server that supports ASP.NET/C\#. In addition, any data storage medium that can be abstracted through our data layer will be supported, either in our initial release or through future community development efforts.
%Our development environment is Microsoft Visual Studio 2008, with Microsoft Server 2008 Standard Edition and Microsoft SQL Server 2008 Enterprise Edition.
